Cluster creation

To successfully create a cluster, please provide the required information outlined below. Ensure all details are filled correctly before proceeding with the cluster creation. Copy the block below and complete it with the necessary information for your new cluster:

# required infromation
cluster_name: 
customer_id: 

# other k8s version
(by default latest supported k8s minor version provided by us)
kubernetes_version: 

# controlplane flavor 
# by default s1.medium
flavor: 

## Machine deployments one block per MD (default: 1 md, 3 replicas, s1.large, random AZ)
# machine deployment name
# by default clusterName-az-md
md_name:  
# replicas by default 3
replicas:
# by default s1.large
flavor: 
# by default random-az
availability_zone: 

## add the autoscaler (default: disabled)
min_size:
max_size:

Detailed information about options can be found below.

Optional Settings

The IP ranges can be adjusted for pods in-cluster addresses and the addresses services will get. If not provided, we will use the defaults shown below. Note that these should only be changed if a clash occurs with an externally routed network.

# the IP range for pod allocation
pod_cidr: 172.25.0.0/16

# the IP range for service allocation
service_cidr: 10.96.0.0/12

# the core dns address is the 10th address of the service cidr
dns_service_address: 10.96.0.10

What You Will Receive

After the cluster is created, you will receive an admin kubeconfig through a secure method, along with a WIIT Resource Name for later support queries.

For further communication we need the WIIT Resource Name to identify your cluster.

Detailed Information

Prerequisites

OpenStack Credentials

You must have an existing or newly created OpenStack tenant. In this tenant, create and provide the following:

Required Information for the New Cluster

  • Cluster Name: A maximum of 22 characters.
  • Customer ID: Defaults to the company ID number if not specified.
  • Application Credentials: As mentioned in the prerequisites.

Optional Requirements and Configurable Features (with Default Values)

Kubernetes Version

If not specified, the cluster will be deployed with the latest supported Kubernetes minor version. We support the manual setting of the major.minor (e.g. 1.33), this needs to manual updated if a new version is needed. The Patch level is updated by us and will be automatically deployed.

For more details on supported versions, deprecations, EOL, or other version concerns, click here

OpenStack Network

Provide an existing network ID, or we will create a new network for you. Provided Network will not be deleted, wen the cluster is deleted. They can be reused, after cluster deletion. Automatically created ones will be deleted with cluster deletion.

If you have no special requirements, use the automatically created ones. So you don’t need any creation/cleanup process on our side. For requirements like, shared networks, added VPNs, etc. please use the provides options.

Machine Deployments, Worker Nodes and Autoscaling

For Machine Deployment look into the more detailed docs

As there are a some more options.

Default will get you a single Machine Deployment with 3 Nodes on 1 AZ

Cluster autoscaler (the same for each machineDeployment if more than one)

We support the Cluster Autoscaler which we can activate separately for each Machine Deployment.

Details can be found here